Auditing records are configured as required.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-6850	4.008	SV-29741r1_rule	ECAR-2 ECAR-3	Medium

Description
Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, analyze compromises that have occurred as well as detect an attack that has begun or is about to begin. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Without an audit trail that provides information as to event that occurred and if it was successful or unsuccessful, it is difficult to analyze a series of events to determine the steps used by an attacker to compromise a system or network, or what exactly happened that led to a denial of service. Collecting data such as the successful and unsuccessful events is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.

Description

Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, analyze compromises that have occurred as well as detect an attack that has begun or is about to begin. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Without an audit trail that provides information as to event that occurred and if it was successful or unsuccessful, it is difficult to analyze a series of events to determine the steps used by an attacker to compromise a system or network, or what exactly happened that led to a denial of service. Collecting data such as the successful and unsuccessful events is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior.

STIG	Date
Windows XP Security Technical Implementation Guide	2013-10-01

Details

Check Text ( C-3207r1_chk )
Windows 2000/2003/XP - Analyze the system using the Security Configuration and Analysis snap-in. Expand the Security Configuration and Analysis tree view. Expand the “Local Policies” object and select “Audit Policy”. Compare the settings in the Policy window with the following: Audit account logon events Success,Failure Audit account management Success,Failure Audit directory service access* Failure Audit logon events Success,Failure Audit object access Failure Audit policy change Success Audit priviledge use Failure Audit process tracking No auditing Audit system events Success If system does not audit the events listed above, then this is a finding. Events with a value of “No Auditing” indicate those that are not required by DISA to be audited. *“Audit directory services access” can be set to “No Auditing” for member servers and workstations. If auditing is disabled, then mark this check as a “FINDING.”

Check Text ( C-3207r1_chk )

Windows 2000/2003/XP - Analyze the system using the Security Configuration and Analysis snap-in.
Expand the Security Configuration and Analysis tree view.
Expand the “Local Policies” object and select “Audit Policy”.

Compare the settings in the Policy window with the following:

Audit account logon events Success,Failure
Audit account management Success,Failure
Audit directory service access* Failure
Audit logon events Success,Failure
Audit object access Failure
Audit policy change Success
Audit priviledge use Failure
Audit process tracking No auditing
Audit system events Success

If system does not audit the events listed above, then this is a finding. Events with a value of “No Auditing” indicate those that are not required by DISA to be audited.

*“Audit directory services access” can be set to “No Auditing” for member servers and workstations.

If auditing is disabled, then mark this check as a “FINDING.”

Fix Text (F-6539r1_fix)
Configure the system to audit categories as outlined in check procedure.